Location Constraints

• Selected: The location constraint rule is applied to the locations to which it is assigned.
• Cleared: The location constraint rule is not applied to the locations to which it is assigned.

Note: Setting a constraint to cleared is not the same as removing a location constraint. If you create a new row with the same definition as an existing constraint, choose a new date and clear the active check box, the existing constraint is not turned off at the selected date. If you want to change a location constraint, you must remove all constraints and then redefine the constraints at the date.

Tip: When you clear the Active check box, you make the location constraint rule ineffective without deleting the rule.

The headings that are included in the constraint.

Tip: You can use wildcards to specify more than one heading. To specify the headings using the Wildcard Expression Builder, click the Ellipsis button.

The locations that are included in the constraint.

Tip: You can use wildcards to specify more than one location. To specify the loations using the Wildcard Expression Builder, click the Ellipsis button.

The materials that are included in the constraint.

You can use this field to limit the quantity of specific mined materials from the specified headings and stopes.

The unit for the constraint value. Options are:

• LENGTH
• MASS
• VOLUME
• any user-defined aggregate qualities

The default value is MASS.

The date on which the constraint is applied.

You can use a calendar date or an event. The date or event plus any Delay determines the actual start date. If a date is part way through a period, the location constraint is not applied until the beginning of the following period. If you leave this field blank the start date of the schedule is used.

You use the Calendar button to select a date from a calendar. You use the Ellipsis button to select an event using the Event Builder.

Note: Because there is no way to turn off a location constraint, if there is change to a location constraint at a future date, all location constraints must be redefined at that date.

The delay after the Date/event before the constraint is applied.

The default delay is 0. The delay can be any positive number.

Note: Part days are expressed as decimals, not in HH:MM:SS format.

Usually, delays are used when the Date/event is an event, and the actual date that the event occurs is not known until the schedule is run.

The comments that you want to record for the location constraint rule.